Preserve attachment metadata for external opening - #240
Draft
Xare123 wants to merge 1 commit into
Draft
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Downloaded PDFs and Office documents could exist locally but fail to open because cache paths lacked the original extension and MIME context.
Change
Resolve external-open MIME types from the original filename before falling back to the local path, while preserving unknown-file fallback behavior.
Validation
Focused Flutter tests pass: 7/7 for PDF, DOCX, XLSX, PPTX, text, unknown binary, and local-path fallback.
Non-goals
This does not change attachment downloading, replacement-download scheduling, retries, or message storage.